Introduction

Oracle Insurance Policy Administration (OIPA) uses scheduler applications that initiate in the background in line with the OIPA server initiation. This application picks up all the pending requirements in batches for processing at intervals set by users.

Oracle Customer Support

If you have any questions about the use of our products, our Oracle customers have access to electronic support through My Oracle Support.

Oracle Accessibility

For information about Oracle's commitment to accessibility, visit Oracle Accessibility Learning and Support if you are hearing impaired. For OIPA Accessibility documentation refer to OIPA Accessibility Guide under the Policy Administration Libraries of Oracle Help Center (OHC).

Requirement Processing Engine

The Requirement Processing Engine is a scheduler application in the base code which uses Spring Thread Pool for execution and processing the pending requirements. This application initiates in the background at the time when the OIPA server starts and picks up all the pending requirements in batches for processing at certain intervals. It has replaced the earlier coherence implementation as it was observed that Requirement processing became very heavy and it was, in turn, creating a considerable impact on other coherence processes which lead to OIPA application in a hung state and caused memory issues.

Requirement PAS Properties

The below table lists and illustrates the requirement engine PAS properties. For more information on PAS properties refer to PAS Properties documentation.

Properties	Mandatory	Data Type	Format	Size	Default	Allowed Values	Usage Details
requirement.Service	Yes	Boolean		<=3		Yes/ No	Yes = The requirement Engine will kick off in the background when the server is started. No = The requirement engine will not start in the background.
requirement.service.period	Yes	Unsigned Integer					This is the period in milliseconds after which the requirement engine will try to pick up the pending requirements for processing in batches.
requirement.service.logErrors	No	Boolean		<=3		Yes/ No	Yes =The errors which come up during processing will be logged in the console and Log File No = The error will not be logged. Errors are logged in the ASNBREQUIREMENTERROR Table.
requirement.service.initial.delay	No	Unsigned Integer			0		This is the time period in milliseconds after which the requirement engine should start after the initial server start up. Although it is not mandatory property, but it is recommended to be included as a best practice for better performance.
requirement.service.exclude.status	No					The requirement status values from the ASCODE table	The requirement statuses mentioned in this property will not be picked up for processing by the requirement engine.
requirement.service.corePoolSize	Yes	Unsigned Integer					The batch size of the requirements will be picked for processing at a time.